-- card: 5118 from stack: in
-- bmap block id: 5215
-- flags: 0000
-- background id: 2784
-- name: 


-- part 2 (field)
-- low flags: 01
-- high flags: 0000
-- rect: left=6 top=51 right=312 bottom=505
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 3
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: 


-- part 5 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=474 top=307 right=336 bottom=510
-- title width / last selected line: 0
-- icon id / first selected line: 26425 / 26425
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Next
----- HyperTalk script -----
on mouseUp
  visual effect scroll left
  go to next card
end mouseUp


-- part 6 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=2 top=22 right=51 bottom=38
-- title width / last selected line: 0
-- icon id / first selected line: 29114 / 29114
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Return
----- HyperTalk script -----
on mouseUp
  visual effect iris close
  pop card
end mouseUp



-- part contents for card part 2
----- text -----
In hierarchical databases, the records (things you are storing) are related to each other in a specific manner.  The database is arranged in a hierarchy made up of several levels.  Think of how you might organize a record/CD collection: